An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

App Name: OurHouse App ID: 919471395 We turned in a very necessary update Tuesday August 4th. Heard back from Apple that we got rejected for keywords in our metadata that we've been using successfully for 5+ years and never changed. Those same keywords were used for a submission as recently as 3 weeks ago that went through with no issues. We were told this at 10:44PM PST by 11:14PM my team responded asking what keywords specifically were violating guidelines and it's been complete radio silence since then. We even removed any and all keywords and resubmitted, and now our App has been stuck in review for 6 days. I am pleading for help, I've been stonewalled by every department and cannot reach Apple Review. As I'm writing this I've been waiting for 3 hours for an advisor or anyone to speak with about this. Our app has hundreds of thousands of users that are unable to login currently, our customer service team is completely overloaded and we are out of options. What can we even do? Please help!

Hello Apple Developer Community, I would like to ask for some advice regarding my app review status. App Name: TopRead Apple ID: 6787079131 Submission ID: 20c08ed4-8199-43da-9521-02d0a0f735ae Here is the timeline: July 22: Submitted my app for App Review. July 30: Received a rejection notice from the App Review Team. July 30: Addressed all the issues mentioned in the review feedback and resubmitted the updated version on the same day. Today: It has been 11 days since the resubmission, and the status is still showing "Waiting for Review". I have also contacted Apple Developer Support regarding this matter (Case ID: 20000122447322). However, the response only mentioned that the app is still waiting in the review queue and did not provide an estimated review timeline. We fully understand that App Review requires time and follows a standard process. However, this extended waiting period is beginning to significantly impact our business operations, release schedule, and user expectations. Since we have already addressed the issues from the previous review and submitted the updated version, we would appreciate any advice from the community or Apple team regarding whether this waiting time is normal, or if there are any recommended next steps we should take. Thank you very much for your time and any guidance you can provide. Best regards, TopRead Team

Hello Developer Community, We have submitted our brand new app to the app store that many people worked really hard on. We have been waiting anxiously to see what apple says. However, the app never leaves the "waiting to be reviewed" state, and it has been more than a week since we have uploaded it. We know Apple put back to the queue if we update build and we haven't made any update. Why its taking too long. We have committed a date our clients it will on App Store by 5th Aug (submitted on 30th July) but no work from Apple yet. Now its creating question on crediblity us from our clients.

Hi, I’m experiencing a recurring App Review issue with my app Lux Broker – Tycoon Game. This is not an isolated delayed submission. Almost every recent version of this app has followed the same pattern: Version 1.2.0: waited approximately 7 days before entering review, then review completed in about 5 minutes Version 1.3.0: waited approximately 7 days, then review completed in about 5 minutes Version 1.4.0: waited approximately 7.5 days, then was reviewed/rejected in about 4 minutes Version 1.4.0 resubmission: waited more than 8 days, then was approved in about 5 minutes I am now facing a more urgent situation with version 1.4.1. The currently released version contains a critical production issue that prevents affected users from opening the game. Version 1.4.1 was submitted on August 9, 2026 at 8:57 PM specifically to fix this issue. Because existing users are actively affected, I submitted an Expedited Review Request, and Apple confirmed: “We’ll expedite review for Lux Broker – Tycoon Game.” However, the submission is still in Waiting for Review and has not entered review. I have also contacted Developer Support regarding the issue. Apple ID: 6771816081 Submission ID: 2bb4927f-9a5f-4513-b390-5eec0a0fd216 Support Case: 20000132990094 My concern is not simply that one submission is taking longer than usual. There appears to be a consistent pattern affecting this specific app: submissions remain in “Waiting for Review” for approximately 7–8 days, while the actual review itself consistently takes only a few minutes. This has now become a critical production issue because the currently available version is preventing affected players from accessing the game. The fix is already submitted and the expedited review request has already been approved. Could someone from Apple please check whether this submission is correctly routed to the expedited review queue, or whether there is an app-level review routing issue affecting this application? Any help escalating this to the appropriate App Review team would be greatly appreciated. Thank you.

Hi everyone! I see a lot of people complaining about the same issue: their apps have been stuck in “Waiting for Review” or “In Review” for more than 48 hours. I think Apple should reconsider the wording of their automated email. When they say that 90% of apps are reviewed within 48 hours, it feels quite ambiguous because it doesn’t really explain what happens with the remaining 10%. I see many people waiting more than 48 hours for a review, just like I am. I submitted my app on July 30, 2026, and it still hasn’t been reviewed. The status is still “Waiting for Review.”

I have been waiting a week since I initially posted my app for review. since then there have been no emails, updates, or progress. I tried sending an email through the contact us page in App Store Connect with no response. I even tried calling and I sat on hold waiting for someone to pick up for 4 hours before I had to get off. Case ID: 20000128292512 what else can I do in order to get the ball rolling on this? I need to get it live soon

Dear App Review Team, Our app No.IA (Apple ID: 6768742372) has been in "Waiting for Review" since July 20, 2026. This is version 3.1, resubmitted after the App Review Board cleared Guidelines 2.3.1 and 3.2.1 (Appeal Ticket APL509468). All Guideline 1.1 concerns have been addressed: metadata rewritten, in-app labels updated, screenshots replaced. We have tried: Resolution Center reply, expedited review request, phone call to Developer Support (Case 102912803305). All responses have been generic with no timeline. This app has been in review processes since May 19, 2026 — over 75 days. Any assistance would be greatly appreciated.

I submitted my first public build (iOS 1.0) on July 30th for my game, Golfer's Pair-A-Dice (Apple ID: 6789222313) and it has been in "Waiting for Review" with no movement since then. I read that 24-48 hours is typical, but could take longer for first builds, but it seems like it hasn't even begun to be reviewed which is frustrating. Has anyone experienced similar wait times in the queue and had any success getting their app reviewed? I was hoping to launch on App Store and Google Play Store at same time and Google approved the app in 2 days so it has just been waiting for me to push, which I am waiting on Apple to approve so I can push both simultaneously.

Hi all, I’m building a sandboxed macOS app that, among other things, lets the user create and associate an Apple Note with a calendar meeting. The user explicitly initiates the action. The app uses AppleScript to create the note, obtain its identifier, and open it in Notes. Notes only declares the com.apple.Notes.openlocation scripting access group. Note creation is not covered, so com.apple.security.scripting-targets does not appear sufficient. The working implementation requires: com.apple.security.automation.apple-events com.apple.security.temporary-exception.apple-events for com.apple.Notes NSAppleEventsUsageDescription Has anyone successfully shipped a Mac App Store app using this temporary exception to control the built-in Notes app? Is this potentially acceptable with a clear entitlement explanation and Feedback Assistant report, or should I assume that note creation through AppleScript cannot be included in a Mac App Store build? Is there another supported API that can create an Apple Note and return an identifier or openable URL for it?

Hello Apple, I'm hoping someone can clarify the expected behaviour here, as I'm not sure whether I've missed a step. Timeline for my first submission (iOS 1.0, new organisation account): 21 July — reviewed 22 July — App Review opened a Guideline 2.1 information request, asking the standard set of questions about third-party analytics, third-party advertising, data sharing and any other data collection 23 July — I replied in the App Store Connect message thread with complete answers to all four questions Since then — status has remained In Review, with no further response That's now 18 days. The submission page shows all 19 items as In Review with no warnings, there are no unread messages in the thread, and the version page has no incomplete metadata flags. My questions: When you reply to a 2.1 information request, does the submission automatically return to the review queue, or does replying alone sometimes leave it in a state where it isn't picked back up? Is a reply in the App Store Connect message thread sufficient, or should the response also be entered in the App Review Notes field on the version? Is there anything that would cause a reply to be recorded but not surfaced to the reviewer? I'd rather understand the mechanism than resubmit blindly and lose my place in the queue. Submission ID: 4cd83c15-8977-4545-a1c4-d4e666d769fc App: 6762837701 (com.travellingintime.TravellingInTime) Thanks.

Hi all, Like others my app submission has been stuck in “waiting for review” for weeks. I know initial app reviews take longer than updates, but this has been delayed far too long and makes me concerned about repeating the process in the future. I submitted this app for review back on Feb 10. It was initially rejected for a minor issue, which I resolved and resubmitted the same day. After that, the build remained in “Waiting for Review” for about two weeks with no further communication. At that point I canceled the submission and resubmitted the build, thinking it may have been stuck in the queue (I now know not to do this next time). Unfortunately the new submission has also been waiting for review for another 9 days now with no messages or updates. I’ve contacted app review support as well (case ID- 102826632729). I understand review times can vary, but delays like this make it difficult for developers to plan launches or push updates when the review process is the only path to distributing apps. As paying members of the Apple Developer Program, we rely heavily on this pipeline functioning reliably. Hoping this post will reach someone from Apple who can help move the process along. If any other devs have suggestions/tips that have worked for them, please share so others in this position can become unblocked. Thanks in advance.

Hello, Our app has been in "Waiting for Review" since August 5, 2026, with no status change and no messages in App Store Connect. App Name: Voxen AI Apple ID: 6790147633 Version: 1.0.0 (132) Submission ID: bd9db3ca-72f9-46ad-ace5-6fdfc873e59f Date Submitted: Aug 5, 2026 at 4:49 PM Could someone from App Review check whether this submission is stuck in the queue, or let us know if any action is needed on our side? Thank you.

Why does Apple’s App Store Connect app (iPadOS) hide the submission status of a testflight submission? The Build has: Testflight, General Filesizes tabs, but none of them show the TestFlight release status. Release 3.2 .

App ID 6794306744. Version 1.2.0 submitted 2 August, still "Waiting for Review" — six business days at the time of writing. I'm not posting to ask anyone to speed it up. I have a specific question about how expedited review requests are supposed to behave. I submitted two expedited review requests for this version. I have received: no confirmation that either request was received no notification that either was declined and I can find no representation of the request anywhere — not in App Store Connect, and not in the App Store Connect API So from my side a submitted expedite request is indistinguishable from one that was declined, and from one that never arrived at all. Is this the intended behaviour? On previous versions of this app expedite requests were granted within minutes, so I know the mechanism works — I just can't tell what happened this time. Two related questions for anyone who knows: Is there any surface (UI or API) where the status of an expedited review request can be seen? I've looked at reviewSubmissions and appStoreVersions and there's nothing there. Does an account lose access to expedited review silently after repeated requests? If so, is that communicated anywhere? For context on the submission itself: 7 items (the version plus two auto-renewable subscriptions and three non-consumables), all showing "Ready for Review", no errors, no missing metadata, build in VALID processing state. This is the first version of this app to include in-app purchases. Two support requests (5 and 8 August) have not been answered yet. If anyone else is currently seeing unusually long Waiting for Review times on a first submission containing IAPs, I'd be interested to know — it would help tell a systemic queue issue apart from something specific to my account.

Hi everyone, I submitted my first iOS app for App Review over 72 hours ago, and the status is still “Waiting for Review.” I contacted Apple Developer Support about 30 hours ago regarding the delay, but I haven't received a response yet. I understand that review times can vary, but the app hasn't moved to “In Review” at all. I haven't removed or resubmitted the app because I don't want to restart the review process. Has anyone experienced similar waiting times recently? How long did it take for your app to move from “Waiting for Review” to “In Review”?

Hello everyone, I'm facing a frustrating issue with the new App Store Connect UI when trying to submit In-App Purchases alongside my app version. My Situation: App: Nagpur Prime Property (iOS) Rejected under Guideline 2.1(b) — App Completeness Reason: IAPs not submitted with the binary What I've Done: Uploaded new Build 7 (v1.0.1) ✅ Created 2 auto-renewable subscriptions: • Basic Plan (npp_basic_plan) — Ready for Review ✅ • Premium Plan (npp_premium_plan) — Ready for Review ✅ Added both to a Draft Submission (3 items total) ✅ Sandbox tester account added ✅ The Problem: The Draft Submission panel shows: ⚠️ "Unable to Submit for Review — To submit your items for review, add an app version for the selected platform." The "Submit for Review" button is permanently GRAYED OUT. The Draft Submission shows: Versions column: "-" (no app version linked) Items: 3 (Subscription Group + 2 subscriptions) The App Version (Build 7) is in a SEPARATE submission showing "Ready for Review" — but there is NO UI option to link the two submissions together. What I've Tried: Clicking "Add for Review" from Subscription Group page Clicking "Add for Review" from individual plan pages Clicking "Draft Submissions (1)" from version page Contacted Apple Review team — no solution provided Tried "Resubmit to App Review" on version — IAPs not included Question: In Apple's new App Store Connect UI, how do you correctly link an IAP Draft Submission to an App Version submission so they can be reviewed together? Is there a specific order of operations that needs to be followed? Or is there a known workaround for this issue? Thank you in advance!

Dear App Review Team, Our app – Apple ID 6743036315 has been stuck in the “Waiting for Review” status for over 7 days (since August 3, 2026). Normally, reviews begin within a few days, but in our case, it seems unusually delayed. Ive just had some exposure in the local newspapers and wanted to capitalise on this and keep these new customers hence a very important update. I risk losing business at a critical time. Could you please clarify: • Is there a specific reason for this extended hold? • Is any action required from our side? • When can we expect the review to proceed? Thank you very much for your time and assistance.

Hello everyone, I have already released four apps, and I am currently experiencing an issue where the review process appears to be stuck while trying to release my fifth app. The app was rejected several times due to In-App Purchase related issues, and the most recent rejection was on July 15. I submitted the app for review again on July 16, but there was no progress. On July 24, I canceled the existing review submission and submitted it again with the updated version. However, as of today, August 10, the review still has not progressed. I have also contacted Apple Developer Support twice, but I have not received any response at all. Could the review be stuck because I canceled the previously rejected submission and submitted a corrected version again? In addition, I developed another new app and submitted it for review on August 4, but that submission also has not progressed. Could anyone advise me on how I can move the review process forward? Thank you.

Hello Apple Developer Community & Support Staff, I am writing this out of sheer desperation. Our app has been stuck in the overall review process for nearly TWO MONTHS. Regarding our latest submission: Submission ID: aec29b9a-fbdf-41f3-b617-d593c2e29f70 Date Submitted: August 3, 2026 We completely understand that as a dating app, our submission requires strict adherence to UGC guidelines, robust user reporting/blocking mechanisms, and thorough content filtering. We have meticulously implemented all of these safety features and addressed every single issue previously raised by the review team. Recently, the status of this August 3rd submission finally changed to "In Review," which gave us hope. However, it inexplicably rolled back to "Waiting for Review" shortly after, with ZERO communication, messages, or explanations provided in the Resolution Center. We are hemorrhaging funds daily on server costs, delayed marketing campaigns, and operational expenses due to this silent, indefinite hold. If our app was escalated to a specialized team, or if there is a system glitch, we at least deserve to be informed. Could an Apple representative here please look into this specific Submission ID? We urgently need someone to manually check why this rollback happened and help us move forward. We are 100% ready to cooperate. Thank you.

Hello, My QueenBoard app update was submitted more than four days ago and is still awaiting a review decision. There are no messages in the Resolution Center and no requests for additional information. Details: App: QueenBoard - Logic Puzzle Games Apple ID: 6774414102 Platform: iOS Version: 1.2.4 Build: 26 Submitted: July 26, 2026 at 6:40 PM Current status: In Review Submission ID: 1d5aa681-6804-4aab-9a2c-50c411d856de This is an update to an existing app that has already been approved and published. All required app information has been completed, and I have not received any notice indicating that action is required from me. Could someone confirm whether the review is proceeding normally or whether there is anything I need to provide? Thank you for your help. Best regards, Tim Nguyen